Despawn entities when the mod that spawned them is despawned #33
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
EngoDev
approved these changes
Jan 17, 2026
Collaborator
Author
|
Whoops, targeting the wrong branch. Cherry-picked and merged as 9470a68 |
MarcGuiselin
added a commit
that referenced
this pull request
Jan 17, 2026
Implement `ModDespawnBehaviour`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a mod spawns an entity on
ModStartupand then gets reloaded there will be multiple duplicate entities in the world.This pr adds tracking for entities spawned by a mod. If the mod is unloaded (despawned) or hot-reloaded the entities from the old version will be despawned. I think this is closer to what a user expects.
This behaviour is configurable and opt out via
ModloaderPlugin::set_despawn_behaviour(ModDespawnBehaviour::None).Depends on #31